Pages
  • life with BSD
  • 2026-07-23 The I'll get to it later problem... for FreeBSD
  • 2026-07-13 On the closing of open searchable sites around OSS projects
  • 2026-06-09 Implementation monocultures
  • 2026-05-28 Using the units command to convert celsius to fahrenheit on FreeBSD
  • 2026-05-11 Trying out spinel on FreeBSD and fixed the blog feeds
  • 2026-04-27 Getting more information on a FreeBSD pkg without installing it
  • 2026-04-19 Feeling sherlocked - XDG's new Projects folder
  • 2026-04-07 The Laptop Integration Testing project
  • 2026-01-02 Migrating from bastille auto-starting jails from deprecated bastille_list
  • 2025-12-23 Understanding more about the pkg-status service for FreeBSD
  • 2025-12-07 Trying out flow control binaries for FreeBSD
  • 2025-11-07 Swift nightly preview for FreeBSD
  • 2025-11-02 Using jujutsu in a git compatible way to track freebsd ports
  • 2025-10-28 The sherlocking of the gemini protocol
  • 2025-10-09 How to change the options in a freebsd port
  • 2025-09-16 Waiting on Swift mainline for FreeBSD
  • 2025-08-25 Dmesg for Cable Matters USB 3.1 to 4 port Gigabit Ethernet Adapter
  • 2025-08-15 Generate a QR code with typst
  • 2025-07-31 Fixing jujutsu and leaky ascii escape sequences on FreeBSD
  • 2025-07-31 Swift now available as a package for FreeBSD
  • 2025-07-28 The FreeBSD project clarifies its stance on gen-ai powered contributions
  • 2025-07-28 The rustup question
  • 2025-07-08 Goodbye old friend, a tale
  • 2025-06-30 Configuring FreeBSD to network with a postmarketos phone over usb
  • 2025-06-25 swift (re)lands in the FreeBSD ports tree
  • 2025-06-24 typst a rust powered typesetting tool aiming at latex
  • 2025-06-19 Open Source Two Worlds thoughts
  • 2025-06-14 Taking a look at repolocli
  • 2025-06-09 Zig master builds now with FreeBSD support
  • 2025-06-07 Finding rust dependencies in Makefile.crates
  • 2025-06-05 Ripgrep or ripgrep-all
  • 2025-06-02 Ripgrep a nice Rust utility for ports spelunking
  • 2025-05-31 Get started with gpui on FreeBSD
  • 2025-05-29 Query freshports with Deno
  • 2025-05-27 Trying out Defuddle an npm tool via Deno
  • 2025-05-25 Deno for FreeBSD
  • 2025-05-23 A new beginning
life with BSD
  • life with BSD
  • 2026-07-23 The I'll get to it later problem... for FreeBSD
  • 2026-07-13 On the closing of open searchable sites around OSS projects
  • 2026-06-09 Implementation monocultures
  • 2026-05-28 Using the units command to convert celsius to fahrenheit on FreeBSD
  • 2026-05-11 Trying out spinel on FreeBSD and fixed the blog feeds
  • 2026-04-27 Getting more information on a FreeBSD pkg without installing it
  • 2026-04-19 Feeling sherlocked - XDG's new Projects folder
  • 2026-04-07 The Laptop Integration Testing project
  • 2026-01-02 Migrating from bastille auto-starting jails from deprecated bastille_list
  • 2025-12-23 Understanding more about the pkg-status service for FreeBSD
  • 2025-12-07 Trying out flow control binaries for FreeBSD
  • 2025-11-07 Swift nightly preview for FreeBSD
  • 2025-11-02 Using jujutsu in a git compatible way to track freebsd ports
  • 2025-10-28 The sherlocking of the gemini protocol
  • 2025-10-09 How to change the options in a freebsd port
  • 2025-09-16 Waiting on Swift mainline for FreeBSD
  • 2025-08-25 Dmesg for Cable Matters USB 3.1 to 4 port Gigabit Ethernet Adapter
  • 2025-08-15 Generate a QR code with typst
  • 2025-07-31 Fixing jujutsu and leaky ascii escape sequences on FreeBSD
  • 2025-07-31 Swift now available as a package for FreeBSD
  • 2025-07-28 The FreeBSD project clarifies its stance on gen-ai powered contributions
  • 2025-07-28 The rustup question
  • 2025-07-08 Goodbye old friend, a tale
  • 2025-06-30 Configuring FreeBSD to network with a postmarketos phone over usb
  • 2025-06-25 swift (re)lands in the FreeBSD ports tree
  • 2025-06-24 typst a rust powered typesetting tool aiming at latex
  • 2025-06-19 Open Source Two Worlds thoughts
  • 2025-06-14 Taking a look at repolocli
  • 2025-06-09 Zig master builds now with FreeBSD support
  • 2025-06-07 Finding rust dependencies in Makefile.crates
  • 2025-06-05 Ripgrep or ripgrep-all
  • 2025-06-02 Ripgrep a nice Rust utility for ports spelunking
  • 2025-05-31 Get started with gpui on FreeBSD
  • 2025-05-29 Query freshports with Deno
  • 2025-05-27 Trying out Defuddle an npm tool via Deno
  • 2025-05-25 Deno for FreeBSD
  • 2025-05-23 A new beginning

2026-07-23 The I'll get to it later problem... for FreeBSD

I like scanning all manners of projects that pop up in the OSS spectrum. Lots of it are itches scratched (If I had a quarter for every OSS itch scratched...) which is not a bad thing to see. Sometimes the most mundane itch scratcher is exactly what one needs (or someone else wants).

However, one trend that seems to be common among newer projects is to only provide binaries for the following platforms: Windows, Mac, Linux.

A project that goes the extra effort to provide pre-built binaries I would imagine is probably aiming to hit one or more of these goals:

  • Ease adoption

  • Simplify the deployment process

  • Ensure code-quality to a particular bar

  • Be more than just a mind dump of source code

This leaves a user of FreeBSD usually as an after thought when it is mainly the WinMacLin triumverate platforms that are being targeted. I imagine it also would cultivate in the more persistent FreeBSD user a form of thicker skin when it comes to finding software that solves needs since relying on upstream projects to provide something will get answers like "No" or "We will get to it later" or "What is FreeBSD?" (I guess 'patches accepted' as a response has become a trigger phrase as of late if phrased poorly which imo is a social regression).

There are probably quite a few different causes that lead to the "We will get to it later" and I am going to leave it as an exercise to the reader to puzzle through what are some causes. One personal observation (the rest are yours to find) is that certain sets of code repository level freebies encourages this "later" behavior.

So, being left out of the release party what does a determined FreeBSD user do? Here are some options:

  • Figure out if the linuxlator can handle the job

  • Learn about the ports (and package) system

  • Handle the code packaging

  • Port it yourself (FreeBSD bugs would probably be happy to receive contributions)

I guess one takeaway from all of this is that being left out of options is an opportunity to create some of your own.

PREVRANDOMNEXT